| V-219557 | High | The telnet daemon must not be running. | The telnet protocol uses unencrypted network communication, which means that data from the login session, including passwords and all other information transmitted during the session, can be... |
| V-219558 | High | The rlogind service must not be running. | The rlogin service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be... |
| V-209019 | High | The x86 Ctrl-Alt-Delete key sequence must be disabled. | A locally logged-on user who presses Ctrl-Alt-Delete, when at the console, can reboot the system. If accidentally pressed, as could happen in the case of mixed OS environment, this can create the... |
| V-208807 | High | The system must not have accounts configured with blank or null passwords. | If an account has an empty password, anyone could log in and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments. |
| V-219957 | High | The Oracle Linux operating system must not contain .shosts or shosts.equiv files. | The .shosts and shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the... |
| V-219560 | High | The SSH daemon must be configured to use only the SSHv2 protocol. | SSH protocol version 1 suffers from design flaws that result in security vulnerabilities and should not be used. |
| V-209043 | High | The snmpd service must not use a default password. | Presence of the default SNMP password enables querying of different system aspects and could result in unauthorized knowledge of the system. |
| V-209040 | High | The TFTP daemon must operate in secure mode which provides access only to a single directory on the host file system. | Using the "-s" option causes the TFTP service to only serve files from the given directory. Serving files from an intentionally specified directory reduces the risk of sharing files which should... |
| V-209031 | High | The NFS server must not have the insecure file locking option enabled. | Allowing insecure file locking could allow for sensitive data to be viewed or edited by an unauthorized user. |
| V-208915 | High | The rshd service must not be running. | The rsh service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen... |
| V-208914 | High | The rsh-server package must not be installed. | The "rsh-server" package provides several obsolete and insecure network services. Removing it decreases the risk of those services' accidental (or intentional) activation. |
| V-208913 | High | The telnet-server package must not be installed. | Removing the "telnet-server" package decreases the risk of the unencrypted telnet service's accidental (or intentional) activation.
Mitigation: If the telnet-server package is configured to only... |
| V-224675 | High | The Oracle Linux operating system must be a vendor-supported release. | An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security... |
| V-219547 | High | There must be no .rhosts or hosts.equiv files on the system. | Trust files are convenient, but when used in conjunction with the R-services, they can allow unauthenticated access to a system. |
| V-219543 | High | Vendor-provided cryptographic certificates must be installed to verify the integrity of system software. | This key is necessary to cryptographically verify packages that packages are from the operating system vendor. |
| V-209076 | High | The Oracle Linux 6 operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. | Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The operating system must implement cryptographic modules adhering to the higher... |
| V-208926 | High | The SSH daemon must not allow authentication using an empty password. | Configuring this setting for the SSH daemon provides additional assurance that remote login via SSH will require a password, even in the event of misconfiguration elsewhere. |
| V-208916 | High | The rexecd service must not be running. | The rexec service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen... |
| V-219551 | Medium | The system must employ a local IPv4 firewall. | The "iptables" service provides the system's host-based firewalling capability for IPv4 and ICMP. |
| V-219550 | Medium | The operating system must prevent public IPv6 access into an organizations internal networks, except as appropriately mediated by managed interfaces employing boundary protection devices. | The "ip6tables" service provides the system's host-based firewalling capability for IPv6 and ICMPv6. |
| V-219553 | Medium | The operating system must prevent public IPv4 access into an organizations internal networks, except as appropriately mediated by managed interfaces employing boundary protection devices. | The "iptables" service provides the system's host-based firewalling capability for IPv4 and ICMP. |
| V-219552 | Medium | The operating system must connect to external networks or information systems only through managed IPv4 interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture. | The "iptables" service provides the system's host-based firewalling capability for IPv4 and ICMP. |
| V-219555 | Medium | The operating system must support the requirement to centrally manage the content of audit records generated by organization defined information system components. | A log server (loghost) receives syslog messages from one or more systems. This data can be used as an additional log source in the event a system is compromised and its local logs are suspect.... |
| V-219554 | Medium | The systems local IPv4 firewall must implement a deny-all, allow-by-exception policy for inbound packets. | In "iptables" the default policy is applied only after all the applicable rules in the table are examined for a match. Setting the default policy to "DROP" implements proper design for a firewall,... |
| V-219559 | Medium | The TFTP service must not be running. | Disabling the "tftp" service ensures the system is not acting as a tftp server, which does not provide encryption or authentication. |
| V-209015 | Medium | The system package management tool must verify ownership on all files and directories associated with the audit package. | Ownership of audit binaries and configuration files that is incorrect could allow an unauthorized user to gain privileges that they should not have. The ownership set by the vendor should be... |
| V-209014 | Medium | The system package management tool must verify permissions on all files and directories associated with the audit package. | Permissions on audit binaries and configuration files that are too generous could allow an unauthorized user to gain privileges that they should not have. The permissions set by the vendor should... |
| V-209017 | Medium | The system package management tool must verify contents of all files associated with the audit package. | The hash on important files like audit system executables should match the information given by the RPM database. Audit executables with erroneous hashes could be a sign of nefarious activity on... |
| V-209016 | Medium | The system package management tool must verify group-ownership on all files and directories associated with the audit package. | Group-ownership of audit binaries and configuration files that is incorrect could allow an unauthorized user to gain privileges that they should not have. The group-ownership set by the vendor... |
| V-209012 | Medium | The system must prohibit the reuse of passwords within five iterations. | Preventing reuse of previous passwords helps ensure that a compromised password is not reused by a user. |
| V-209018 | Medium | There must be no world-writable files on the system. | Data in world-writable files can be modified by any user on the system. In almost all circumstances, files can be configured using a combination of user and group permissions to support whatever... |
| V-208935 | Medium | The graphical desktop environment must have automatic lock enabled. | Enabling the activation of the screen lock after an idle period ensures password entry will be required in order to access the system, preventing access by passersby. |
| V-208934 | Medium | The graphical desktop environment must automatically lock after 15 minutes of inactivity and the system must require user reauthentication to unlock the environment. | Enabling idle activation of the screen saver ensures the screensaver will be activated after the idle delay. Applications requiring continuous, real-time screen display (such as network management... |
| V-208838 | Medium | The system must use a FIPS 140-2 approved cryptographic hashing algorithm for generating account password hashes (login.defs). | Using a stronger hashing algorithm makes password cracking attacks more difficult. |
| V-208839 | Medium | The system must use a FIPS 140-2 approved cryptographic hashing algorithm for generating account password hashes (libuser.conf). | Using a stronger hashing algorithm makes password cracking attacks more difficult. |
| V-208933 | Medium | The graphical desktop environment must set the idle timeout to no more than 15 minutes. | Setting the idle delay controls when the screensaver will start, and can be combined with screen locking to prevent access from passersby. |
| V-208836 | Medium | The system must disable accounts after three consecutive unsuccessful logon attempts. | Locking out user accounts after a number of incorrect attempts prevents direct password guessing attacks. |
| V-208837 | Medium | The system must use a FIPS 140-2-approved cryptographic hashing algorithm for generating account password hashes (system-auth). | Using a stronger hashing algorithm makes password-cracking attacks more difficult. |
| V-208830 | Medium | System and application account passwords must be changed at least annually. | Any password, no matter how complex, can eventually be cracked. Therefore, system and application account passwords need to be changed periodically. If an organization fails to change the system... |
| V-208918 | Medium | The ypbind service must not be running. | Disabling the "ypbind" service ensures the system is not acting as a client in a NIS or NIS+ domain. |
| V-209065 | Medium | The mail system must forward all mail for root to one or more system administrators. | A number of system services utilize email messages sent to the root user to notify system administrators of active or impending issues. These messages must be forwarded to at least one monitored... |
| V-208799 | Medium | The system must use a Linux Security Module at boot time. | Disabling a major host protection feature, such as SELinux, at boot time prevents it from confining system services at boot time. Further, it increases the chances that it will remain off during... |
| V-208798 | Medium | System security patches and updates must be installed and up-to-date. | Installing software updates is a fundamental mitigation against the exploitation of publicly-known vulnerabilities. |
| V-208828 | Medium | User passwords must be changed at least every 60 days. | Setting the password maximum age ensures users are required to periodically change their passwords. This could possibly decrease the utility of a stolen password. Requiring shorter password... |
| V-208827 | Medium | Users must not be able to change passwords more than once every 24 hours. | Setting the minimum password age protects against users cycling back to a favorite password after satisfying the password reuse requirement. |
| V-208826 | Medium | The system must require passwords to contain a minimum of 15 characters. | Requiring a minimum password length makes password cracking attacks more difficult by ensuring a larger search space. However, any security benefit from an onerous requirement must be carefully... |
| V-208823 | Medium | Library files must be owned by a system account. | Files from shared library directories are loaded into the address space of processes (including privileged ones) or of the kernel itself at runtime. Proper ownership is necessary to protect the... |
| V-208822 | Medium | Library files must have mode 0755 or less permissive. | Files from shared library directories are loaded into the address space of processes (including privileged ones) or of the kernel itself at runtime. Restrictive permissions are necessary to... |
| V-208820 | Medium | The /etc/group file must be group-owned by root. | The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
| V-209072 | Medium | The sudo command must require authentication. | The "sudo" command allows authorized users to run programs (including shells) as other users, system users, and root. The "/etc/sudoers" file is used to configure authorized "sudo" users as well... |
| V-208825 | Medium | All system command files must be owned by root. | System binaries are executed by privileged users as well as system services, and restrictive permissions are necessary to ensure that their execution of these programs cannot be co-opted. |
| V-208824 | Medium | All system command files must have mode 755 or less permissive. | System binaries are executed by privileged users, as well as system services, and restrictive permissions are necessary to ensure execution of these programs cannot be co-opted. |
| V-208821 | Medium | The /etc/group file must have mode 0644 or less permissive. | The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
| V-208812 | Medium | The /etc/shadow file must have mode 0000. | The "/etc/shadow" file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security. Failure to give ownership of this file to... |
| V-208813 | Medium | The /etc/gshadow file must be owned by root. | The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security. |
| V-208810 | Medium | The /etc/shadow file must be owned by root. | The "/etc/shadow" file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security. Failure to give ownership of this file to... |
| V-208811 | Medium | The /etc/shadow file must be group-owned by root. | The "/etc/shadow" file stores password hashes. Protection of this file is critical for system security. |
| V-208816 | Medium | The /etc/passwd file must be owned by root. | The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security. |
| V-208817 | Medium | The /etc/passwd file must be group-owned by root. | The "/etc/passwd" file contains information about the users that are configured on the system. Protection of this file is critical for system security. |
| V-208815 | Medium | The /etc/gshadow file must have mode 0000. | The /etc/gshadow file contains group password hashes. Protection of this file is critical for system security. |
| V-208818 | Medium | The /etc/passwd file must have mode 0644 or less permissive. | If the "/etc/passwd" file is writable by a group-owner or the world the risk of its compromise is increased. The file contains the list of accounts on the system and associated information, and... |
| V-208819 | Medium | The /etc/group file must be owned by root. | The "/etc/group" file contains information regarding groups that are configured on the system. Protection of this file is important for system security. |
| V-208931 | Medium | If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms. | The ssl directive specifies whether to use ssl or not. If not specified it will default to "no". It should be set to "start_tls" rather than doing LDAP over SSL. |
| V-208930 | Medium | Mail relaying must be restricted. | This ensures "postfix" accepts mail messages (such as cron job reports) from the local system only, and not from the network, which protects it from network attack. |
| V-208806 | Medium | Default operating system accounts, other than root, must be locked. | Disabling authentication for default system accounts makes it more difficult for attackers to make use of them to compromise a system. |
| V-209042 | Medium | The snmpd service must use only SNMP protocol version 3 or newer. | Earlier versions of SNMP are considered insecure, as they potentially allow unauthorized access to detailed system management information. |
| V-208800 | Medium | A file integrity baseline must be created. | For AIDE to be effective, an initial database of "known-good" information about files must be captured and it should be able to be verified against the installed files. |
| V-208809 | Medium | The root account must be the only account having a UID of 0. | An account has root authority if it has a UID of 0. Multiple accounts with a UID of 0 afford more opportunity for potential intruders to guess a password for a privileged account. Proper... |
| V-208808 | Medium | The /etc/passwd file must not contain password hashes. | The hashes for all user account passwords should be stored in the file "/etc/shadow" and never in "/etc/passwd", which is readable by all users. |
| V-209071 | Medium | The noexec option must be added to the /tmp partition. | Allowing users to execute binaries from world-writable directories such as "/tmp" should never be necessary in normal operation and can expose the system to potential compromise. |
| V-208881 | Medium | The audit system must switch the system to single-user mode when available audit storage volume becomes dangerously low. | Administrators should be made aware of an inability to record audit records. If a separate partition or logical volume of adequate size is used, running low on space for audit records should never occur. |
| V-208880 | Medium | The system must rotate audit log files that reach the maximum file size. | Automatically rotating logs (by setting this to "rotate") minimizes the chances of the system unexpectedly running out of disk space by being overwhelmed with log data. However, for systems that... |
| V-209059 | Medium | The audit system must take appropriate action when there are disk errors on the audit storage volume. | Taking appropriate action in case of disk errors will minimize the possibility of losing audit records. |
| V-209058 | Medium | The audit system must take appropriate action when the audit storage volume is full. | Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records. |
| V-209051 | Medium | The system must be configured to require the use of a CAC, PIV compliant hardware token, or Alternate Logon Token (ALT) for authentication. | Smart card login provides two-factor authentication stronger than that provided by a username/password combination. Smart cards leverage a PKI (public key infrastructure) in order to provide and... |
| V-209050 | Medium | The FTPS/FTP service on the system must be configured with the Department of Defense (DoD) login banner. | This setting will cause the system greeting banner to be used for FTP connections as well. |
| V-209053 | Medium | Audit log files must have mode 0640 or less permissive. | If users can write to audit logs, audit trails can be modified or destroyed. |
| V-209052 | Medium | The operating system, upon successful logon/access, must display to the user the number of unsuccessful logon/access attempts since the last successful logon/access. | Users need to be aware of activity that occurs regarding their account. Providing users with information regarding the number of unsuccessful attempts that were made to login to their account... |
| V-209055 | Medium | Audit log directories must have mode 0755 or less permissive. | If users can delete audit logs, audit trails can be modified or destroyed. |
| V-209054 | Medium | Audit log files must be owned by root. | If non-privileged users can write to audit logs, audit trails can be modified or destroyed. |
| V-209056 | Medium | The operating system, upon successful logon, must display to the user the date and time of the last logon or access via ssh. | Users need to be aware of activity that occurs regarding their account. Providing users with information regarding the date and time of their last successful login allows the user to determine if... |
| V-219582 | Medium | The system must require administrator action to unlock an account locked by excessive failed login attempts. | Locking out user accounts after a number of incorrect attempts prevents direct password guessing attacks. Ensuring that an administrator is involved in unlocking locked accounts draws appropriate... |
| V-219583 | Medium | The system must disable accounts after excessive login failures within a 15-minute interval. | Locking out user accounts after a number of incorrect attempts within a specific period of time prevents direct password guessing attacks. |
| V-219581 | Medium | The Bluetooth service must be disabled. | Disabling the "bluetooth" service prevents the system from attempting connections to Bluetooth devices, which entails some security risk. Nevertheless, variation in this risk decision may be... |
| V-219586 | Medium | The operating system must conduct backups of system-level information contained in the information system per organization defined frequency to conduct backups that are consistent with recovery time and recovery point objectives. | Operating system backup is a critical step in maintaining data assurance and availability. System-level information includes system-state information, operating system and application software,... |
| V-219584 | Medium | The operating system must enforce requirements for the connection of mobile devices to operating systems. | USB storage devices such as thumb drives can be used to introduce unauthorized software and other vulnerabilities. Support for these devices should be disabled and the devices themselves should be... |
| V-219585 | Medium | The operating system must conduct backups of user-level information contained in the operating system per organization defined frequency to conduct backups consistent with recovery time and recovery point objectives. | Operating system backup is a critical step in maintaining data assurance and availability. User-level information is data generated by information system and/or application users. Backups shall be... |
| V-219588 | Medium | The systems local IPv6 firewall must implement a deny-all, allow-by-exception policy for inbound packets. | In "ip6tables" the default policy is applied only after all the applicable rules in the table are examined for a match. Setting the default policy to "DROP" implements proper design for a... |
| V-219589 | Medium | The Oracle Linux 6 operating system must use a virus scan program. | Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems.
The virus scanning software should be... |
| V-208870 | Medium | All rsyslog-generated log files must be owned by root. | The log files generated by rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Log files should be protected from unauthorized access. |
| V-208871 | Medium | All rsyslog-generated log files must be group-owned by root. | The log files generated by rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Log files should be protected from unauthorized access. |
| V-208872 | Medium | All rsyslog-generated log files must have mode 0600 or less permissive. | Log files can contain valuable information regarding system configuration. If the system log files are not protected, unauthorized users could change the logged data, eliminating their forensic value. |
| V-208873 | Medium | The operating system must back up audit records on an organization defined frequency onto a different system or media than the system being audited. | A log server (loghost) receives syslog messages from one or more systems. This data can be used as an additional log source in the event a system is compromised and its local logs are suspect.... |
| V-208875 | Medium | The operating system must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event. | Ensuring the "auditd" service is active ensures audit records generated by the kernel can be written to disk, or that appropriate actions will be taken if other obstacles exist. |
| V-208876 | Medium | The operating system must employ automated mechanisms to facilitate the monitoring and control of remote access methods. | Ensuring the "auditd" service is active ensures audit records generated by the kernel can be written to disk, or that appropriate actions will be taken if other obstacles exist. |
| V-208877 | Medium | The operating system must produce audit records containing sufficient information to establish what type of events occurred. | Ensuring the "auditd" service is active ensures audit records generated by the kernel can be written to disk, or that appropriate actions will be taken if other obstacles exist. |
| V-208878 | Medium | The system must retain enough rotated audit logs to cover the required log retention period. | The total storage for audit log files must be large enough to retain log information over the period required. This is a function of the maximum log file size and the number of logs retained. |
| V-208879 | Medium | The system must set a maximum audit log file size. | The total storage for audit log files must be large enough to retain log information over the period required. This is a function of the maximum log file size and the number of logs retained. |
| V-219568 | Medium | The system must have a host-based intrusion detection tool installed. | Adding host-based intrusion detection tools can provide the capability to automatically take actions in response to malicious behavior, which can provide additional agility in reacting to network... |
| V-208804 | Medium | The system must prevent the root account from logging in from virtual consoles. | Preventing direct root login to virtual console devices helps ensure accountability for actions taken on the system using the root account. |
| V-219561 | Medium | The SSH daemon must be configured to use only FIPS 140-2 approved ciphers. | Approved algorithms should impart some level of confidence in their implementation. These are also required for compliance. |
| V-219562 | Medium | The system clock must be synchronized continuously, or at least daily. | Enabling the "ntpd" service ensures that the "ntpd" service will be running and that the system will synchronize its time to any servers specified. This is important whether the system is... |
| V-219563 | Medium | The system clock must be synchronized to an authoritative DoD time source. | Synchronizing with an NTP server makes it possible to collate system logs from multiple sources or correlate computer events with real time events. Using a trusted NTP server provided by your... |
| V-219564 | Medium | The LDAP client must use a TLS connection using trust certificates signed by the site CA. | The tls_cacertdir or tls_cacertfile directives are required when tls_checkpeer is configured (which is the default for openldap versions 2.1 and up). These directives define the path to the trust... |
| V-208848 | Medium | The system must implement virtual address space randomization. | Address space layout randomization (ASLR) makes it more difficult for an attacker to predict the location of attack code he or she has introduced into a process's address space during an attempt... |
| V-209024 | Medium | The DHCP client must be disabled if not needed. | DHCP relies on trusting the local network. If the local network is not trusted, then it should not be used. However, the automatic configuration provided by DHCP is commonly used and the... |
| V-208801 | Medium | The system must use a Linux Security Module configured to enforce limits on system services. | Setting the SELinux state to enforcing ensures SELinux is able to confine potentially compromised processes to the security policy, which is designed to prevent them from causing damage to the... |
| V-209021 | Medium | The sendmail package must be removed. | The sendmail software was not developed with security in mind and its design prevents it from being effectively contained by SELinux. Postfix should be used instead. |
| V-208863 | Medium | The system must use a reverse-path filter for IPv4 network traffic when possible on all interfaces. | Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface they were received on. It should not be used on systems which are... |
| V-208862 | Medium | The system must be configured to use TCP syncookies when experiencing a TCP SYN flood. | A TCP SYN flood attack can cause a denial of service by filling a system's TCP connection table with connections in the SYN_RCVD state. Syncookies can be used to track a connection when a... |
| V-208867 | Medium | The Stream Control Transmission Protocol (SCTP) must be disabled unless required. | Disabling SCTP protects the system against exploitation of any flaws in its implementation. |
| V-208866 | Medium | The Datagram Congestion Control Protocol (DCCP) must be disabled unless required. | Disabling DCCP protects the system against exploitation of any flaws in its implementation. |
| V-208865 | Medium | The system must ignore ICMPv6 redirects by default. | An illicit ICMP redirect message could result in a man-in-the-middle attack. |
| V-208864 | Medium | The system must use a reverse-path filter for IPv4 network traffic when possible by default. | Enabling reverse path filtering drops packets with source addresses that should not have been able to be received on the interface they were received on. It should not be used on systems which are... |
| V-208869 | Medium | The Transparent Inter-Process Communication (TIPC) protocol must be disabled unless required. | Disabling TIPC protects the system against exploitation of any flaws in its implementation. |
| V-208843 | Medium | The system boot loader must require authentication. | Password protection on the boot loader configuration ensures users with physical access cannot trivially alter important bootloader settings. These include which kernel to use, and whether to... |
| V-219579 | Medium | The systems local firewall must implement a deny-all, allow-by-exception policy for forwarded packets. | In "iptables" the default policy is applied only after all the applicable rules in the table are examined for a match. Setting the default policy to "DROP" implements proper design for a firewall,... |
| V-219578 | Medium | The Bluetooth kernel module must be disabled. | If Bluetooth functionality must be disabled, preventing the kernel from loading the kernel module provides an additional safeguard against its activation. |
| V-219569 | Medium | X Windows must not be enabled unless required. | Unnecessary services should be disabled to decrease the attack surface of the system. |
| V-219573 | Medium | The operating system must employ automated mechanisms to detect the presence of unauthorized software on organizational information systems and notify designated organizational officials in accordance with the organization defined frequency. | By default, AIDE does not install itself for periodic execution. Periodically running AIDE may reveal unexpected changes in installed files. |
| V-219572 | Medium | The operating system must employ automated mechanisms, per organization defined frequency, to detect the addition of unauthorized components/devices into the operating system. | By default, AIDE does not install itself for periodic execution. Periodically running AIDE may reveal unexpected changes in installed files. |
| V-219571 | Medium | A file integrity tool must be used at least weekly to check for unauthorized file changes, particularly the addition of unauthorized system libraries or binaries, or for unauthorized modification to authorized system libraries or binaries. | By default, AIDE does not install itself for periodic execution. Periodically running AIDE may reveal unexpected changes in installed files. |
| V-219570 | Medium | Wireless network adapters must be disabled. | The use of wireless networking can introduce many different attack vectors into the organization’s network. Common attack vectors such as malicious association and ad hoc networks will allow an... |
| V-219577 | Medium | The audit system must provide a warning when allocated audit record storage volume reaches a documented percentage of maximum audit record storage capacity. | Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption. |
| V-219576 | Medium | The operating system must ensure unauthorized, security-relevant configuration changes detected are tracked. | By default, AIDE does not install itself for periodic execution. Periodically running AIDE may reveal unexpected changes in installed files. |
| V-219575 | Medium | The operating system must detect unauthorized changes to software and information. | By default, AIDE does not install itself for periodic execution. Periodically running AIDE may reveal unexpected changes in installed files. |
| V-219574 | Medium | The operating system must provide a near real-time alert when any of the organization defined list of compromise or potential compromise indicators occurs. | By default, AIDE does not install itself for periodic execution. Periodically running AIDE may reveal unexpected changes in installed files. |
| V-208849 | Medium | The system must limit the ability of processes to have simultaneous write and execute access to memory. | A common type of exploit is the stack buffer overflow. An application receives from an attacker more data than it is prepared for and stores this information on its stack, writing beyond the... |
| V-209035 | Medium | The Department of Defense (DoD) login banner must be displayed immediately prior to, or as part of, graphical desktop environment login prompts. | An appropriate warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. |
| V-209049 | Medium | There must be no .netrc files on the system. | Unencrypted passwords for remote FTP servers may be stored in ".netrc" files. DoD policy requires passwords be encrypted in storage and not used in access scripts. |
| V-209032 | Medium | The audit system must identify staff members to receive notifications of audit log storage volume capacity issues. | Email sent to the root account is typically aliased to the administrators of the system, who can take appropriate action. |
| V-209034 | Medium | A login banner must be displayed immediately prior to, or as part of, graphical desktop environment login prompts. | An appropriate warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. |
| V-208919 | Medium | The tftp-server package must not be installed unless required. | Removing the "tftp-server" package decreases the risk of the accidental (or intentional) activation of tftp services. |
| V-208917 | Medium | The ypserv package must not be installed. | Removing the "ypserv" package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services. |
| V-208911 | Medium | The xinetd service must be disabled if no network services utilizing it are enabled. | The xinetd service provides a dedicated listener service for some programs, which is no longer necessary for commonly-used network services. Disabling it ensures that these uncommon services are... |
| V-208910 | Medium | The audit system must be configured to audit the loading and unloading of dynamic kernel modules. | The addition/removal of kernel modules can be used to alter the behavior of the kernel and potentially introduce malicious code into kernel space. It is important to have an audit trail of modules... |
| V-208857 | Medium | The system must not accept IPv4 source-routed packets by default. | Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
| V-208854 | Medium | The system must not accept ICMPv4 redirect packets on any interface. | Accepting ICMP redirects has few legitimate uses. It should be disabled unless it is absolutely required. |
| V-208855 | Medium | The system must not accept ICMPv4 secure redirect packets on any interface. | Accepting "secure" ICMP redirects (from those gateways listed as default gateways) has few legitimate uses. It should be disabled unless it is absolutely required. |
| V-208852 | Medium | IP forwarding for IPv4 must not be enabled, unless the system is a router. | IP forwarding permits the kernel to forward packets from one network interface to another. The ability to forward packets between two networks is only appropriate for systems acting as routers. |
| V-208853 | Medium | The system must not accept IPv4 source-routed packets on any interface. | Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
| V-208850 | Medium | The system must not send ICMPv4 redirects by default. | Sending ICMP redirects permits the system to instruct other systems to update their routing information. The ability to send ICMP redirects is only appropriate for systems acting as routers. |
| V-208851 | Medium | The system must not send ICMPv4 redirects from any interface. | Sending ICMP redirects permits the system to instruct other systems to update their routing information. The ability to send ICMP redirects is only appropriate for systems acting as routers. |
| V-208858 | Medium | The system must not accept ICMPv4 secure redirect packets by default. | Accepting "secure" ICMP redirects (from those gateways listed as default gateways) has few legitimate uses. It should be disabled unless it is absolutely required. |
| V-219548 | Medium | The system must employ a local IPv6 firewall. | The "ip6tables" service provides the system's host-based firewalling capability for IPv6 and ICMPv6. |
| V-219549 | Medium | The operating system must connect to external networks or information systems only through managed IPv6 interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture. | The "ip6tables" service provides the system's host-based firewalling capability for IPv6 and ICMPv6. |
| V-219546 | Medium | A file integrity tool must be installed. | The AIDE package must be installed if it is to be available for integrity checking. |
| V-219544 | Medium | The system package management tool must cryptographically verify the authenticity of system software packages during installation. | Ensuring the validity of packages' cryptographic signatures prior to installation ensures the provenance of the software and protects against malicious tampering. |
| V-219542 | Medium | The audit system must alert designated staff members when the audit storage volume approaches capacity. | Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption. |
| V-208842 | Medium | The system boot loader configuration file(s) must have mode 0600 or less permissive. | Proper permissions ensure that only the root user can modify important boot parameters. |
| V-219958 | Medium | The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. | DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. The only SSHv2 hash algorithm meeting this requirement is SHA. |
| V-209070 | Medium | The login user list must be disabled. | Leaving the user list enabled is a security risk since it allows anyone with physical access to the system to quickly enumerate known user accounts without logging in. |
| V-209008 | Medium | Remote file systems must be mounted with the nodev option. | Legitimate device files should only exist in the /dev directory. NFS mounts should not present device files to users. |
| V-209009 | Medium | Remote file systems must be mounted with the nosuid option. | NFS mounts should not present suid binaries to users. Only vendor-supplied suid executables should be installed to their default location on the local filesystem. |
| V-209066 | Medium | Audit log files must be group-owned by root. | If non-privileged users can write to audit logs, audit trails can be modified or destroyed. |
| V-208927 | Medium | The SSH daemon must be configured with the Department of Defense (DoD) login banner. | The warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. Alternatively, systems whose ownership should not be obvious... |
| V-208923 | Medium | The SSH daemon must ignore .rhosts files. | SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
| V-208920 | Medium | The cron service must be running. | Due to its usage for maintenance and security-supporting tasks, enabling the cron daemon is essential. |
| V-208814 | Medium | The /etc/gshadow file must be group-owned by root. | The "/etc/gshadow" file contains group password hashes. Protection of this file is critical for system security. |
| V-208924 | Medium | The SSH daemon must not allow host-based authentication. | SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
| V-208925 | Medium | The system must not permit root logins using remote access programs such as ssh. | Permitting direct root login reduces auditable information about who ran privileged commands on the system and also allows direct attack attempts on root's password. |
| V-208841 | Medium | The system boot loader configuration file(s) must be group-owned by root. | The "root" group is a highly-privileged group. Furthermore, the group-owner of this file should not have any access privileges anyway. |
| V-208840 | Medium | The system boot loader configuration file(s) must be owned by root. | Only root should be able to modify important boot parameters. |
| V-208845 | Medium | The system must not permit interactive boot. | Using interactive boot, the console user could disable auditing, firewalls, or other services, weakening system security. |
| V-208844 | Medium | The system must require authentication upon booting into single-user and maintenance modes. | This prevents attackers with physical access from trivially bypassing security on the machine and gaining root access. Such accesses are further prevented by configuring the bootloader password. |
| V-208847 | Medium | The Department of Defense (DoD) login banner must be displayed immediately prior to, or as part of, console login prompts. | An appropriate warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. |
| V-209067 | Medium | The system must provide automated support for account management functions. | A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. Enterprise environments... |
| V-219556 | Low | The audit system must be configured to audit all use of setuid and setgid programs. | Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to... |
| V-209011 | Low | The system must use SMB client signing for connecting to samba servers using mount.cifs. | Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit. |
| V-209010 | Low | The system must use SMB client signing for connecting to samba servers using smbclient. | Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit. |
| V-209013 | Low | The operating system must protect the confidentiality and integrity of data at rest. | The risk of a system's physical compromise, particularly mobile systems such as laptops, places its data at risk of compromise. Encrypting this data mitigates the risk of its loss if the system is lost. |
| V-208937 | Low | The Automatic Bug Reporting Tool (abrtd) service must not be running. | Mishandling crash data could expose sensitive information about vulnerabilities in software executing on the local machine, as well as sensitive information from within a process's address space... |
| V-208936 | Low | The system must display a publicly-viewable pattern during a graphical desktop environment session lock. | Setting the screensaver mode to blank-only conceals the contents of the display from passersby. |
| V-208932 | Low | The openldap-servers package must not be installed unless required. | Unnecessary packages should not be installed to decrease the attack surface of the system. |
| V-208834 | Low | The system must require passwords to contain at least one lower-case alphabetic character. | Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space. |
| V-208835 | Low | The system must require at least eight characters be changed between the old and new passwords during a password change. | Requiring a minimum number of different characters during password changes ensures that newly changed passwords should not resemble previously compromised ones. Note: Passwords which are changed... |
| V-208831 | Low | The system must require passwords to contain at least one numeric character. | Requiring digits makes password guessing attacks more difficult by ensuring a larger search space. |
| V-208832 | Low | The system must require passwords to contain at least one uppercase alphabetic character. | Requiring a minimum number of uppercase characters makes password guessing attacks more difficult by ensuring a larger search space. |
| V-208833 | Low | The system must require passwords to contain at least one special character. | Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space. |
| V-209023 | Low | The xorg-x11-server-common (X Windows) package must not be installed, unless required. | Unnecessary packages should not be installed to decrease the attack surface of the system. |
| V-209064 | Low | The system package management tool must verify contents of all files associated with packages. | The hash on important files like system executables should match the information given by the RPM database. Executables with erroneous hashes could be a sign of nefarious activity on the system. |
| V-209060 | Low | The NFS server must not have the all_squash option enabled. | The "all_squash" option maps all client requests to a single anonymous uid/gid on the NFS server, negating the ability to track file access by user ID. |
| V-209061 | Low | The system package management tool must verify ownership on all files and directories associated with packages. | Ownership of system binaries and configuration files that is incorrect could allow an unauthorized user to gain privileges that they should not have. The ownership set by the vendor should be... |
| V-209062 | Low | The system package management tool must verify group-ownership on all files and directories associated with packages. | Group-ownership of system binaries and configuration files that is incorrect could allow an unauthorized user to gain privileges that they should not have. The group-ownership set by the vendor... |
| V-209063 | Low | The system package management tool must verify permissions on all files and directories associated with packages. | Permissions on system binaries and configuration files that are too generous could allow an unauthorized user to gain privileges that they should not have. The permissions set by the vendor should... |
| V-208829 | Low | Users must be warned 7 days in advance of password expiration. | Setting the password warning age enables users to make the change at a practical time. |
| V-208797 | Low | The Red Hat Network Service (rhnsd) service must not be running, unless it is being used to query the Oracle Unbreakable Linux Network for updates and information. | Although systems management and patching is extremely important to system security, management by a system outside the enterprise enclave is not desirable for some environments. However, if the... |
| V-208796 | Low | The system must use a separate file system for user home directories. | Ensuring that "/home" is mounted on its own partition enables the setting of more restrictive mount options, and also helps ensure that users cannot trivially fill partitions used for log or audit... |
| V-208793 | Low | The system must use a separate file system for /tmp. | The "/tmp" partition is used as temporary storage by many programs. Placing "/tmp" in its own partition enables the setting of more restrictive mount options, which can help protect programs which use it. |
| V-208940 | Low | The oddjobd service must not be running. | The "oddjobd" service may provide necessary functionality in some environments but it can be disabled if it is not needed. Execution of tasks by privileged programs, on behalf of unprivileged... |
| V-209068 | Low | Auditing must be enabled at boot by setting a kernel parameter. | Each process on the system carries an "auditable" flag which indicates whether its activities can be audited. Although "auditd" takes care of enabling this for all processes which launch after it... |
| V-208942 | Low | The rdisc service must not be running. | General-purpose systems typically have their network and routing information configured statically by a system administrator. Workstations or some special-purpose systems often use DHCP (instead... |
| V-209069 | Low | Automated file system mounting tools must not be enabled unless needed. | All filesystems that are required for the successful operation of the system should be explicitly listed in "/etc/fstab" by an administrator. New filesystems should not be arbitrarily introduced... |
| V-209074 | Low | The Oracle Linux operating system must mount /dev/shm with the nosuid option. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid"... |
| V-208909 | Low | The audit system must be configured to audit changes to the /etc/sudoers file. | The actions taken by system administrators should be audited to keep a record of what was executed on the system, as well as, for accountability purposes. |
| V-209044 | Low | The system default umask for the bash shell must be 077. | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read and/or written to... |
| V-209025 | Low | All GIDs referenced in /etc/passwd must be defined in /etc/group. | Inconsistency in GIDs between /etc/passwd and /etc/group could lead to a user having unintended rights. |
| V-209075 | Low | The Oracle Linux operating system must mount /dev/shm with the noexec option. | The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files as they may be incompatible.... |
| V-208898 | Low | The audit system must be configured to audit all discretionary access control permission modifications using fchownat. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208899 | Low | The audit system must be configured to audit all discretionary access control permission modifications using fremovexattr. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208892 | Low | The audit system must be configured to audit modifications to the systems Mandatory Access Control (MAC) configuration (SELinux). | The system's mandatory access policy (SELinux) should not be arbitrarily changed by anything other than administrator action. All changes to MAC policy should be audited. |
| V-208893 | Low | The audit system must be configured to audit all discretionary access control permission modifications using chmod. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208890 | Low | The operating system must automatically audit account termination. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be... |
| V-208891 | Low | The audit system must be configured to audit modifications to the systems network configuration. | The network environment should not be modified by anything other than administrator action. Any change to network parameters should be audited. |
| V-208896 | Low | The audit system must be configured to audit all discretionary access control permission modifications using fchmodat. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208897 | Low | The audit system must be configured to audit all discretionary access control permission modifications using fchown. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208894 | Low | The audit system must be configured to audit all discretionary access control permission modifications using chown. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208895 | Low | The audit system must be configured to audit all discretionary access control permission modifications using fchmod. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-219541 | Low | The system must use a separate file system for the system audit data path. | Placing "/var/log/audit" in its own partition enables better separation between audit files and other files, and helps ensure that auditing cannot be halted due to the partition running out of space. |
| V-209046 | Low | The system default umask in /etc/profile must be 077. | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read and/or written to... |
| V-209047 | Low | The system default umask in /etc/login.defs must be 077. | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read and/or written to... |
| V-208803 | Low | All device files must be monitored by the system Linux Security Module. | If a device file carries the SELinux type "unlabeled_t", then SELinux cannot properly restrict access to the device file. |
| V-208802 | Low | The system must use a Linux Security Module configured to limit the privileges of system services. | Setting the SELinux policy to "targeted" or a more specialized policy ensures the system will confine processes that are likely to be targeted for exploitation, such as network or system services. |
| V-209048 | Low | The system default umask for daemons must be 027 or 022. | The umask influences the permissions assigned to files created by a process at run time. An unnecessarily permissive umask could result in files being created with insecure permissions. |
| V-208794 | Low | The system must use a separate file system for /var. | Ensuring that "/var" is mounted on its own partition enables the setting of more restrictive mount options. This helps protect system services such as daemons or other programs which use it. It is... |
| V-208889 | Low | The operating system must automatically audit account disabling actions. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be... |
| V-208888 | Low | The operating system must automatically audit account modification. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be... |
| V-208885 | Low | The audit system must be configured to audit all attempts to alter system time through clock_settime. | Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such... |
| V-208884 | Low | The audit system must be configured to audit all attempts to alter system time through stime. | Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such... |
| V-208887 | Low | The operating system must automatically audit account creation. | In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be... |
| V-208886 | Low | The audit system must be configured to audit all attempts to alter system time through /etc/localtime. | Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such... |
| V-208883 | Low | The audit system must be configured to audit all attempts to alter system time through settimeofday. | Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such... |
| V-208882 | Low | The audit system must be configured to audit all attempts to alter system time through adjtimex. | Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such... |
| V-208939 | Low | The ntpdate service must not be running. | The "ntpdate" service may only be suitable for systems which are rebooted frequently enough that clock drift does not cause problems between reboots. In any event, the functionality of the ntpdate... |
| V-208938 | Low | The atd service must be disabled. | The "atd" service could be used by an unsophisticated insider to carry out activities outside of a normal login session, which could complicate accountability. Furthermore, the need to schedule... |
| V-209057 | Low | The system must allow locking of graphical desktop sessions. | The ability to lock graphical desktop sessions manually allows users to easily secure their accounts should they need to depart from their workstations temporarily. |
| V-219580 | Low | The system must provide VPN connectivity for communications over untrusted networks. | Providing the ability for remote users or systems to initiate a secure VPN connection protects information when it is transmitted over a wide area network. |
| V-219587 | Low | The system must forward audit records to the syslog service. | The auditd service does not include the ability to send audit records to a centralized server for management directly. It does, however, include an audit event multiplexor plugin (audispd) to... |
| V-208874 | Low | System logs must be rotated daily. | Log files that are not properly rotated run the risk of growing so large that they fill up the /var/log partition. Valuable logging information could be lost if the /var/log partition becomes full. |
| V-208907 | Low | The audit system must be configured to audit successful file system mounts. | The unauthorized exportation of data to external media could result in an information leak where classified information, Privacy Act information, and intellectual property could be lost. An audit... |
| V-208805 | Low | The system must prevent the root account from logging in from serial consoles. | Preventing direct root login to serial port interfaces helps ensure accountability for actions taken on the systems using the root account. |
| V-219565 | Low | The noexec option must be added to removable media partitions. | Allowing users to execute binaries from removable media such as USB keys exposes the system to potential compromise. |
| V-219566 | Low | The operating system must employ cryptographic mechanisms to protect information in storage. | The risk of a system's physical compromise, particularly mobile systems such as laptops, places its data at risk of compromise. Encrypting this data mitigates the risk of its loss if the system is lost. |
| V-219567 | Low | The operating system must employ cryptographic mechanisms to prevent unauthorized disclosure of data at rest unless otherwise protected by alternative physical measures. | The risk of a system's physical compromise, particularly mobile systems such as laptops, places its data at risk of compromise. Encrypting this data mitigates the risk of its loss if the system is lost. |
| V-209045 | Low | The system default umask for the csh shell must be 077. | The umask value influences the permissions assigned to files when they are created. A misconfigured umask value could result in files with excessive permissions that can be read and/or written to... |
| V-209028 | Low | Emergency accounts must be provisioned with an expiration date. | When emergency accounts are created, there is a risk they may remain in place and active after the need for them no longer exists. Account expiration greatly reduces the risk of accounts being... |
| V-209029 | Low | The system must require passwords to contain no more than three consecutive repeating characters. | Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks. |
| V-209026 | Low | All accounts on the system must have unique user or account names. | Unique usernames allow for accountability on the system. |
| V-209027 | Low | Temporary accounts must be provisioned with an expiration date. | When temporary accounts are created, there is a risk they may remain in place and active after the need for them no longer exists. Account expiration greatly reduces the risk of accounts being... |
| V-209020 | Low | The postfix service must be enabled for mail delivery. | Local mail delivery is essential to some system maintenance and notification tasks. |
| V-209022 | Low | The netconsole service must be disabled unless required. | The "netconsole" service is not necessary unless there is a need to debug kernel panics, which is not common. |
| V-208908 | Low | The audit system must be configured to audit user deletions of files and programs. | Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as detecting malicious processes that... |
| V-208904 | Low | The audit system must be configured to audit all discretionary access control permission modifications using removexattr. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208905 | Low | The audit system must be configured to audit all discretionary access control permission modifications using setxattr. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208906 | Low | The audit system must be configured to audit failed attempts to access files and programs. | Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise. |
| V-209041 | Low | The FTP daemon must be configured for logging or verbose mode. | To trace malicious activity facilitated by the FTP service, it must be configured to ensure that all commands sent to the ftp server are logged using the verbose vsftpd log format. The default... |
| V-208900 | Low | The audit system must be configured to audit all discretionary access control permission modifications using fsetxattr. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208901 | Low | The audit system must be configured to audit all discretionary access control permission modifications using lchown. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208902 | Low | The audit system must be configured to audit all discretionary access control permission modifications using lremovexattr. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208903 | Low | The audit system must be configured to audit all discretionary access control permission modifications using lsetxattr. | The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the... |
| V-208861 | Low | The system must ignore ICMPv4 bogus error responses. | Ignoring bogus ICMP error responses reduces log size, although some activity would not be logged. |
| V-208860 | Low | The system must not respond to ICMPv4 sent to a broadcast address. | Ignoring ICMP echo requests (pings) sent to broadcast or multicast addresses makes the system slightly more difficult to enumerate on the network. |
| V-208868 | Low | The Reliable Datagram Sockets (RDS) protocol must be disabled unless required. | Disabling RDS protects the system against exploitation of any flaws in its implementation. |
| V-209039 | Low | All public directories must be owned by a system account. | Allowing a user account to own a world-writable directory is undesirable because it allows the owner of that directory to remove or replace any files that may be placed in the directory by other users. |
| V-209038 | Low | The sticky bit must be set on all public directories. | Failing to set the sticky bit on public directories allows unauthorized users to delete files in the directory structure.
The only authorized public directories are those temporary directories... |
| V-209037 | Low | The operating system must manage information system identifiers for users and devices by disabling the user identifier after an organization defined time period of inactivity. | Disabling inactive accounts ensures that accounts which may not have been responsibly removed are not available to attackers who may have compromised their credentials. |
| V-209036 | Low | Accounts must be locked upon 35 days of inactivity. | Disabling inactive accounts ensures that accounts which may not have been responsibly removed are not available to attackers who may have compromised their credentials. |
| V-209033 | Low | The system must limit users to 10 simultaneous system logins, or a site-defined number, in accordance with operational requirements. | Limiting simultaneous user logins can insulate the system from denial of service problems caused by excessive logins. Automated login processes operating improperly or maliciously may result in an... |
| V-209030 | Low | Process core dumps must be disabled unless needed. | A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers... |
| V-208941 | Low | The qpidd service must not be running. | The qpidd service is automatically installed when the "base" package selection is selected during installation. The qpidd service listens for network connections, which increases the attack... |
| V-208795 | Low | The system must use a separate file system for /var/log. | Placing "/var/log" in its own partition enables better separation between log files and other files in "/var/". |
| V-208912 | Low | The xinetd service must be uninstalled if no network services utilizing it are enabled. | Removing the "xinetd" package decreases the risk of the xinetd service's accidental (or intentional) activation. |
| V-208856 | Low | The system must log Martian packets. | The presence of "martian" packets (which have impossible addresses) as well as spoofed packets, source-routed packets, and redirects could be a sign of nefarious network activity. Logging these... |
| V-208859 | Low | The system must ignore ICMPv4 redirect messages by default. | This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
| V-209073 | Low | The Oracle Linux operating system must mount /dev/shm with the nodev option. | The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity... |
| V-219545 | Low | The system package management tool must cryptographically verify the authenticity of all software packages during installation. | Ensuring all packages' cryptographic signatures are valid prior to installation ensures the provenance of the software and protects against malicious tampering. |
| V-208922 | Low | The SSH daemon must set a timeout count on idle sessions. | This ensures a user login will be terminated as soon as the "ClientAliveCountMax" is reached. |
| V-208921 | Low | The SSH daemon must set a timeout interval on idle sessions. | Causing idle users to be automatically logged out guards against compromises one system leading trivially to compromises on another. |
| V-208928 | Low | The SSH daemon must not permit user environment settings. | SSH environment options potentially allow users to bypass access restriction in some configurations. |
| V-208929 | Low | The avahi service must be disabled. | Because the Avahi daemon service keeps an open network port, it is subject to network attacks. Its functionality is convenient but is only appropriate if the local network can be trusted. |
| V-208846 | Low | The system must be configured so all network connections associated with a communication session are terminated at the end of the session or after 15 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port... |
